docs(en): merge docs-cn/sync-docs into docs-cn/dev @ 9dac0cd8#970
Conversation
✅ Deploy Preview for cn-vitest ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7176033272
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| function artifacts(): ReadonlyArray<TestArtifact> | ||
| ``` | ||
|
|
||
| <<<<<<< HEAD |
There was a problem hiding this comment.
This commit leaves raw conflict markers (<<<<<<<, =======, >>>>>>>) in the page, which means the merge was not actually resolved and the published documentation will render broken content with both alternatives mixed together. Please resolve the conflict by choosing the intended text and deleting the markers.
Useful? React with 👍 / 👎.
| ## viteEnvironment <Version>4.1.0</Version> {#viteenvironment} | ||
| ## logs <Version>5.0.0</Version> {#logs} | ||
|
|
||
| <<<<<<< HEAD |
There was a problem hiding this comment.
The logs section still includes unresolved merge conflict markers, so the file contains two competing blocks in one document and will ship malformed Markdown. This should be resolved by keeping the correct final content and removing all conflict marker lines.
Useful? React with 👍 / 👎.
3 participants
此 PR 自动生成。
合并 vitest-dev/docs-cn 的修改至本仓库（@ 9dac0cd）
以下文件存在冲突，可能需要重新翻译：
请解决所有冲突后提交到此 pull request，可直接在 Github 修改、切换到 sync-9dac0cd8-1 分支进行修改或者使用 Github Desktop 拉取此 pr 修改并提交。
禁止使用 Squash Merge 来合并此 Pull Request！
使用该操作会导致上游仓库的内容丢失，并致使下一次合并产生冲突。